Copyright: © Copyright Agilent Technologies, 2000, 2001


Sharing Data

There are several ways to share data between the 89600 analyzer and other applications or programs:

•	Saving and recalling traces

•	Saving and recalling recordings

•	Copying and pasting traces

•	Using the ADS interface

•	Using the COM API

•	Using VBScript Macros

See Also

Using Data Registers


Saving and Recalling Traces

Path: File > Save > Save Trace or File > , Recall > , Recall Trace

When you save a trace, the analyzer actually saves the measurement data that is displayed. This may include more data than is actually displayed in the trace. You can choose whether or not to save the Data Header with the trace.

Note

When you save a trace and expect to recall it again with the same appearance as when it was saved, you must save it with the data header.

When you recall a trace, it goes into a data register.

You can save traces from the analyzer and recall them back into the analyzer or into several other programs and applications. You can also recall into the analyzer traces that were saved from other programs and applications. The analyzer supports the following file formats:

•	CSV (comma delimited ASCII), *.CSV

•	Mat-file (MATLAB®†), *.MAT

•	Mat-file (MATLAB Version 4), *.MAT

•	SDF, *.SDF, *.DAT, *.CAP

•	Text (Tab delimited ASCII), *.TXT

CSV and Text files are ASCII. MATLAB and SDF files are binary.

If you are saving traces and will be recalling them back into an 89600-series analyzer, any of the formats will work. The MATLAB format is the most compact.

If you are saving or recalling traces to or from another program or application, you must use the format that is compatible with that program or application.

Note

You cannot recall E3238S snapshot files into a trace. You must recall the files as a recording.

See Also

Sharing Data

Copying and Pasting Traces

Using Data Registers

†MATLAB is a U.S. registered trademark of The Math Works, Inc.


Saving and Recalling Recordings

Path: File > Save > Save Recording or File > , Recall > , Recall Recording

You can also save and recall recordings. See About Recordings.

You can save recordings in any of the formats listed for saving/recalling files, with one addition. You can save recordings in two different SDF formats:

•	The SDF (Fast) format uses cardinal spans, and the data is uncorrected. (Internal correction information is saved with the recording, but corrections are not applied to the data until you play it back.)

•	The SDF (Export) format resamples to user spans and the data is corrected.

In general, you should use the SDF (Export) format only if you will be importing the recording into another application that requires resampled, corrected data. This is especially useful for exporting data to ADS.

Note that files saved in SDF (Export) format are limited to less than 268 million points. If you save a larger recording, the file is truncated at 268 million points.

You can recall into an 89600 analyzer files that were saved in SDF (Export) format, but you will lose some triggering information. If you plan to recall the recording into an 89600 analyzer, it is safest to save it in the SDF (Fast) format.

When you save a recording, only a subset of the Data Header variables are saved with the file.

You can recall time snapshot files from the Agilent E3238S as recordings.

Important

When recalling a recording from an 89400-series analyzer, make sure the recording was created using a cardinal span. If the recording was created using a non-cardinal span, the 89600 VSA software cannot accurately recreate and apply time corrections.


Copying and Pasting Traces

You can copy and paste traces into other Windows applications. For example, you can copy an 89600 trace and paste it into an Excel spreadsheet. For detailed instructions, see Porting Data to Other Applications.

See Also

Sharing Data

Saving and Recalling Traces

Using Data Registers


CSV (Comma delimited)

You can save 89600 traces as a comma-separated variable (CSV) ASCII format and open the file in a program that supports CSV files, then use that program to perform statistical analyses or to format results for inclusion in reports and presentations.

The data is saved as an array. For real data, the data appears as a single column. For complex data, the data appears as two columns, with the real part in the first column and the imaginary part in the second column. The number of rows depends on the number of frequency points in the measured data.

For traces saved from the Spectrum Analyzer application, each line of Y data contains two values, the minimum and maximum for the bin. In addition, another set of Y data, called AltY, is listed after the Y data. The AltY data has the same number of lines as the Y data, but each line contains a single value—the sum of power in each bin. The AltY data is used to compute band power when you turn on band power markers in the Spectrum Analyzer application.

If you save the data header with the trace, it appears above the data, with the variable name in the first column and its value in the second column.

The list separator (or delimiter) in the .CSV file depends on your computer's setting in the Regional Settings under Control Panel. In the U.S., for example, the default is a comma, while in Europe the default is a tab.


E3238S Time Snapshot

You can recall (as a recording) time snapshot files saved from the Agilent E3238S Signals Development System. The files can be in either "Signal Capture" or "Big Signal Capture" format (filename.CAP). The files are recalled as recordings, and all normal recording playback features can be applied.

Tip

For most recordings, the analyzer makes an internal copy of the file to use for playback. For E3238S snapshot files, the analyzer does not make a copy because the files are usually quite large and copying them slows down measurement startup. Because the files are not copied, you must not move the E3238 file while playing it back as a recording.

The following restrictions apply:

•	Time domain snapshot files only.

•	The file size is limited to 2 gigasamples. For files larger than 2 gigasamples, the time recording will be truncated to the maximum allowed.

•	You cannot save files in this format, but only recall as recording for playback.

•	Data is resampled during playback.

Note

Both SDF files and E3238S snapshot files use the CAP extension, but the formats are different. You cannot recall an E3238S snapshot file as an SDF file. Likewise, you cannot recall an SDF file as an E3238S snapshot file.


MAT-File

You can generate a signal in MATLAB, then recall it into the analyzer for display and/or further manipulation. You can also save a recording or trace from the analyzer, recall it into MATLAB for data analysis, save and recall the recording or trace back into the analyzer for display.

Two MATLAB formats are supported: version 4 and earlier, and version 5 or newer. Both versions use the same file extension, MAT.

Besides saving and recalling MATLAB files, you can also use the COM API to program and control the 89600 analyzer directly from a MATLAB program. The COM API online help includes a MATLAB Measurement Demo example program that shows you how to use MATLAB to access the COM API.

You can also make calls to MATLAB directly from the 89600 analyzer using VBScript and the Macro feature. See Sample Macros for a sample macro that uses MATLAB.


SDF (Fast)
SDF

The SDF file formats allow you to recall traces saved by 89400-series analyzers. You can also import SDF files into Agilent Technologies EEsof ADS. The default file suffixes are *.SDF, *.DAT, and *.CAP. Note the following when recalling traces from 89400-series analyzers:

•	By default, 89600 VSA software shows recalled traces at the trace's cardinal acquisition span. Therefore, traces from 89440 or 89441 analyzers that were acquired at full span will show a 10 MHz span in 89600 VSA software.

•	Time corrections are accurate in traces from 89400-series analyzers that were acquired using a cardinal span.

Important

When recalling a trace from an 89400-series analyzer, make sure the trace was created using a cardinal span. If the trace was created using a non-cardinal span, the 89600 VSA software cannot accurately recreate and apply time corrections.

•	89600 VSA software cannot demodulate VSB signals from 89400-series analyzers. 89600 VSA software performs VSB demodulation at a 12 MHz span whereas the default span in 89400-series analyzers is 7 MHz.

See Saving and Recalling Recordings for more information about SDF file format for recordings.


Text (Tab delimited)

You can save 89600 traces or recordings as a tab delimited ASCII file (*.TXT). You can recall the file into any program/application that supports text files (for example, Microsoft Excel).

For real data, each line in the file contains a single value. For complex data, each line contains two values, with the real part first, followed by a tab and the imaginary part. The number of lines depends on the number of frequency points in the measured data.

For traces saved from the Spectrum Analyzer application, each line of Y data contains two values, the minimum and maximum for the bin. In addition, another set of Y data, called AltY, is listed after the Y data. The AltY data has the same number of lines as the Y data, but each line contains a single value—the sum of power in each bin. The AltY data is used to compute band power when you turn on band power markers in the Spectrum Analyzer application.

If you save the data header with the trace, it appears in the file above the data, with the variable name first, followed by a tab and the variable's value.

You can also generate a signal and recall it into the analyzer for analysis and/or display.


About the Data Header
Data Header Variables

When you save a trace or recording, the analyzer appends a data header to the beginning of the file. (You can choose to save the trace without the data header.) The data header contains a list of variables that describe the measurement data. Some of the variables provide information about how the analyzer was set up for the measurement (for example input range, number of averages, and window type). Other variables provide information about the measurement data itself (for example, if overloads occurred). The T_ variables provide information about how the data was displayed.

When you save a trace and expect to recall it again with the same appearance as when it was saved, you must save it with the data header.

Recording data header variables:

• FreqValidMax	• InputZoom
• FreqValidMin	• XStart
• InputCenter	• XDelta
• InputRange	• XDomain
• InputRange1	• XUnit
• InputRange2	• Y(or Y1 and Y2)
• InputRefImped	• YUnit
Trace data header variables

The data header may contain any of the following variables. The variables stored in the data header depend on the type of data contained in the trace.

NOTE

The T_ variables provide information about how the trace display was set up to view the measurement results.

• AliasedData  • AltY  • AverageType  • Avg2DCount  • Avg2DType  • ChannelNum  • CurrentNumAverages  • DataOverload  • DataQuestionable  • DataRealTime  • DataValid  • Demod3GActBaseClass  • Demod3GActChans  • Demod3GCDComposite  • Demod3GChanErrInfo  • Demod3GChipRate  • Demod3GCodeOrder  • Demod3GCompErrInfo  • DemodAttrib  • DemodBitsPerSymbol  • DemodErrors  • DemodErrTbl  • DemodModStatus  • DemodErrInfo  • DemodOFDMSubcarStrt  • DemodOFDMSubcarType  • DemodOutputPtsPerSymbol  • DemodStatePos  • DemodSymbolRate  • DemodType  • FreqValidMax  • FreqValidMin  • InputBlockSize  • InputCenter  • InputConnector  • InputImpedance  • InputRange  • InputRange1  • InputRange2  • InputRefImped  • InputSpan  • InputZoom  • MinMax  • PassThru  • PdfRangeError  • PdfRmsLevel  • PdfUnit  • PowerData  • ResBW  • S_TimeSec  • SweepDone  • SweepOverload  • SwpTime	• T_Aperture  • T_DemodCodeOrder  • T_DemodFreqUnit  • T_DemodStateShape  • T_DemodStateSize  • T_DemodSymbolShape  • T_DemodTblFormat  • T_DemodTimeUnit  • T_PhsOffset  • T_TrigRefLineVis  • T_UnwrapRef  • T_VectXCtr  • T_XEyeLength  • T_XLeft  • T_XLog  • T_XRight  • T_XScaleAuto  • T_YBottom  • T_YCoordinate  • T_YRefPos  • T_YTop  • T_YUnit  • TimeSec  • TimeString  • TotalPdfPoints  • TrcLedBits  • TrcLedBold  • TrcLedReason  • TrcLedStr  • TrcTtl  • TriggerType  • TS_ColorCount  • TS_ColorMap  • TS_Enhance  • TS_Threshold  • TS_Visible  • WindowType  • XDelta  • XDomain  • XPtsPerSymbol  • XSegmentDelta  • XSegmentDomain  • XSegmentLen  • XSegmentStart  • XSegmentUnit  • XStart  • XUnit  • XValidMax  • XValidMin  • Y  • Y1  • Y2  • YUnit  • ZeroPadding


AliasedData

This is a Data Header variable.

Type = Boolean

If AliasedData is true, the Y data is frequency data that includes frequencies that may contain alias products. The portion of the Y data that is valid, non-aliased, frequency data depends on whether zoom is on.

If zoom is off, the non-aliased data is Y data index 1 through [(<numdatapoints> − 1)/1.28 + 1]. For example, if the number of data points is 1025, then the non-aliased data is the first 801 points.

If zoom is on, the non-aliased data is Y data index [<numdatapoints> × 0.14/1.28 + 1] through [<numdatapoints> × 1.14/1.28 + 1]. For example, if the number of data points is 1024, then the non-aliased data is the 113th point through the 913th point.

The points may be real or complex, depending on the setting of "PowerData".


AltY

This is a Data Header variable.

Type = Array of numbers

AltY is present only for traces saved from the Spectrum Analyzer application. The AltY data has the same number of rows as the Y data, but each line contains a single value—the sum of power in each bin. The AltY data is used to computer band power when you turn on band power markers in the Spectrum Analyzer application.


AverageType

This is a Data Header variable.

Type = Short

AverageType indicates the kind of averaging that was on when the measurement was done.

For a list of the average type associated with each value, see the list for VsaAvgStyle in the COM API Constants Table.


Avg2DCount

This is a Data Header variable.

Type = Long

Avg2DCount indicates the current average counter value for trace data displays that have an X- and Z-data component e.g. OFDM RMS Error Vector Spectrum and OFDM RMS Error Vector Time.

For example, the average counter value for OFDM RMS Error Vector Spectrum trace data is next to the "xRMS" display annotation and indicates the number of symbol-times included in the percent RMS average calculation for each subcarrier.

See Also

Avg2DType

OFDM Error Vector Spectrum trace data

OFDM Error Vector Time trace data


Avg2DType

This is a Data Header variable.

Type = Short

Avg2DType indicates the kind of averaging that was used for trace data results that include an X- and Z-component e.g. OFDM RMS Error Vector Spectrum and OFDM RMS Error Vector Time.

For a list of the average type associated with each value, see the list for VsaAvgStyle in the COM API Constants Table.

See Also

Avg2DCount

OFDM Error Vector Spectrum trace data

OFDM Error Vector Time trace data


ChannelNum

This is a Data Header variable.

Type = Short

ChannelNum indicates whether the data is from channel 1 or channel 2. For single channel analyzers, ChannelNum is always 1. For multi-channel data, such as Frequency Response, this variable is removed.

See Also

Input modules


CurrentNumAverages

This is a Data Header variable.

Type = Long

CurrentNumAverages is an integer, and indicates the current average counter. It starts at 1 at the start of the average, and goes up to the user-specified number of averages. This variable should be present only when averaging is on, and only on results that have been averaged. For example, it would not be present on the "Instantaneous Spectrum."

On an exponential average, the value of CurrentNumAverages goes up to the user-specified number of averages, and then stays at that value for all subsequent scans.

See Also

Count

About Averaging


DataOverload

This is a Data Header variable.

Type = Boolean

If DataOverload is true, there was an overload detected on the input hardware sometime during the block of time data that was used to produce this result.

There may have been undetected overloads even if this variable is false or not present.


DataQuestionable

This is a Data Header variable.

Type = Boolean

If DataQuestionable is true, the data is questionable because of something in the measurement setup. For example, if the RBW is set to a value so large that alias products may affect the data, the data is marked as questionable.


DataRealTime

This is a Data Header variable.

Type = Boolean

If DataRealTime is true, the data was acquired in "real-time." This means that there were no gaps between consecutive blocks of time data. Depending on the span and overlap settings, the consecutive blocks of time data may be overlapped. The DataRealTime value probably is useful only on averaged results.

See Also

Real-Time Bandwidth


DataValid

This is a Data Header variable.

Type = Boolean

If DataValid is missing or true, the trace contains data. If DataValid is false, there is no data.

See Also

DataQuestionable


Demod3GActBaseClass

(Option B7N only)

This is a Data Header variable.

Type = Short

Demod3GActBaseClass is the 3G demod (3GPP or cdma2000) CDP base layer. All inactive channels referenced in the Demod3GActChans array are at this CDP layer.


Demod3GActChans

(Option B7N only)

This is a Data Header variable.

Type = Short array

Demod3GActChans is the 3G demod CDP active channel (layer) array. It is the same size as the Y data and indicates which channels are active and their layer. Inactive channels are indicated by a −1 value. Demod3GActChans is available for both cdma2000 and W-CDMA measurements.


Demod3GCDComposite

(Option B7N only)

This is a Data Header variable.

Type = Boolean

Demod3GCDComposite is set to true if the code-domain power or code-domain error data is "composite" data. (If the data is composite data, it has information about all of the signal's active channels at all symbol rates.) All other traces will either have this variable unset or set to false.


Demod3GChanErrInfo

(Option B7N only)

This is a Data Header variable.

Type = Double array

Demod3GChanErrInfo is roughly the equivalent of the "DemodErrors" array in regular digital demodulation. The array holds error information specific to the user's specified CDMA channel, such as Channel EVM and Channel Magnitude Error.

For a list of the array values and corresponding error information, see the list for VsaTrc3GDemChanInfo in the COM API Constants Table.


Demod3GChipRate

(Option B7N only)

This is a Data Header variable.

Type = Double

Demod3GChipRate is the 3G chip rate for this data. This is available for cdma2000 and W-CDMA measurements.


Demod3GCodeOrder

(Option B7N only)

This is a Data Header variable.

Type = Short

Demod3GCodeOrder is the 3G Code Order for the CDP data. This is available for cdma2000 and W-CDMA measurements.

0	Hadamard
1	Bit Reverse


Demod3GCompErrInfo

(Option B7N only)

This is a Data Header variable.

Type = Double array

Demod3GCompErrInfo is roughly the equivalent of the "DemodErrors" array in regular digital demodulation. The array holds error information on the composite signal, such as Composite EVM and Frequency Error.

For a list of the array values and corresponding error information, see the list for VsaTrc3GDemCompInfo in the COM API Constants Table.


DemodAttrib

This is a Data Header variable.

Type = Boolean

If DemodAttrib is present and true, the data is the result of a demodulation measurement.


DemodBitsPerSymbol

(Option AYA only)

This is a Data Header variable.

Type = Short

DemodBitsPerSymbol indicates the number of Digital Demod bits / symbols.

For more information see Symbol Table.


DemodErrors

(Option AYA only)

This is a Data Header variable.

Type = Array of Floats

DemodErrors is the error/information header accompanying the Digital Demod results. The error parameters are stored in the order as shown in the following list:

For more information, see Symbol Table Error Parameters

ERROR PARAMETER	UNITS
Error vector Magnitude (EVM) or	% rms
FSK Error (FSK err)	[FSK] % rms
Magnitude Error (Mag Err)	% rms
Phase Error (Phase Err)	degrees rms
Frequency Error (Freq Err) or	Hz
Carrier Offset (Carr Ofst)	[FSK] Hz
Amplitude Droop (AmpDroop) or	dB per symbol
Estimated RHO	no units
IQ Offset or	linear units
Deviation or	[FSK] Hz
Pilot level (Pilot Lvl)	[VSB] linear units
IQ Gain Imbalance (IQ Imb)	dB
Quadrature Error (QuadErr)	deg
largest EVM or	% peak
largest FSK Error (FSK Err)	% peak
largest EVM symbol number or	no units
largest FSK Err symbol number	no units
Peak Magnitude Error	% peak
Peak Magnitude Error symbol number or	no units
Symbol Offset	no units
Peak Phase Error	degrees peak
Peak Phase symbol number	no units
Clock Alignment	unused
Main Frequency Error	unused
Amplitude Error	unused
Signal to Noise Ratio (SNR(MER))	dB
RHO	no Units
Peak Error Vector Magnitude (Pk EVM)	%
95% EVM	%


DemodErrTbl

(Option AYA only)

This is a Data Header variable.

Type = Boolean

If DemodErrTbl is true, this result is a Digital Demod error table.


DemodModStatus

(Option AYA only)

This is a Data Header variable.

Type = Long

DemodModStatus is a bit set representing the status of the digital demodulation operation for this data:

SYNC_SEARCH	0x1,	0= off,  1= on
PULSE_SEARCH	0x2,	0= off,  1= on
SYNC_FOUND	0x10000,	0 = not found, 1 = found;  valid only if SYNC_SEARCH = 1
PULSE_FOUND	0x20000,	0 = not found, 1 = found;  valid only if PULSE_SEARCH = 1
CARRIER_UNLOCK	0x10000000,	0 = locked,  1 = unlocked
EQUALIZER	0x20000000,	0 = off,  1 = on
MOD_ERRORS_INVALID	0x40000000,	0 = valid,  1 = invalid


DemodOFDMErrInfo

This is a Data Header variable.

Type = Array of Float

DemodOFDMErrInfo is similar to the DemodErrInfo array used for regular digital demod and the Demod3GChanErrInfo and Demod3GCompErrInfo arrays for 3G digital demod. The values in this array provide summary error information about the OFDM demodulation.

The length of this array is equal to vsaTrcDemOFDMErrInfoCount. The values in this array are:

•	vsaTrcDemOFDMErrInfoEvmRms - The RMS level of the normalized Error Vector for all subcarriers and all symbol times in the measurement. Only the symbol times specified by Meas Interval and Meas Offset are used to compute this. The units are percent.

•	vsaTrcDemOFDMErrInfoEvmPk - The peak magnitude of the normalized Error Vector for all subcarriers and all symbol times in the measurement. Only the symbol times specified by Meas Interval and Meas Offset are used to compute this. The units are percent.

•	vsaTrcDemOFDMErrInfoEvmPkSym - The symbol number of the peak magnitude of the normalized Error Vector. Only the symbol times specified by Meas Interval and Meas Offset are used to compute this.

•	vsaTrcDemOFDMErrInfoMagErrRms - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoMagErrPk - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoMagErrPkSym - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoPhaseErrRms - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoPhaseErrPk - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoPhaseErrPkSym - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoFreqErr - The frequency error, equal to the difference between the measured center subcarrier frequency and the instrument center frequency. The units are Hz. The measured center subcarrier frequency is estimated from both the burst preamble and the data symbol times specified by Meas Interval and Meas Offset.

•	vsaTrcDemOFDMErrInfoIqOffset - The IQ offset of the signal, which is the center subcarrier feedthrough. This is estimated from the burst preamble. The value is a unitless power ratio.

•	vsaTrcDemOFDMErrInfoSyncCorr - The correlation between the burst preamble sync and the ideal sync signal. For 802.11a signals, the correlation is done on the short sync portion of the preamble. For HiperLan/2 signals, the correlation is done on the long sync portion of the preamble because there may not be a short sync present. This value is a unitless value between zero and one, where one is perfect correlation and zero is no correlation.

•	vsaTrcDemOFDMErrInfoLSEvm - Not implemented, set to zero.

•	vsaTrcDemOFDMErrInfoPilotEvm - The RMS level of the normalized Error Vector for the pilot subcarriers at all symbol times in the measurement. Only the symbol times specified by Meas Interval and Meas Offset are used to compute this. The units are percent.

•	saTrcDemOFDMErrInfoCpeRms - The RMS level of the Common Pilot Error. The ideal Common Pilot Error has a magnitude of one and a phase of zero, so this RMS level is really computed from the Common Pilot Error minus one. only the symbol times specified by the Meas Interval and Meas Offset are used to compute this. The units are percent.

•	vsaTrcDemOFDMErrInfoOctets - The number of decoded octets in the burst (one octet is eight bits), as detected in the SIGNAL symbol. The value does not include the bits in the SIGNAL symbol itself. For HiperLan/2 signals, the value is specified as 1e10, meaning that the value does not apply and should be displayed as "N/A".

•	vsaTrcDemOFDMErrInfoNSym - The number of symbols in the burst, after the SIGNAL symbol, as detected in the SIGNAL symbol. For HiperLan/2 signals, the value is specified as 1e10, meaning that the value does not apply and should be displayed as "N/A".

•	vsaTrcDemOFDMErrInfoCodingRateNum - The numerator of the coding rate of the convolutional coder, as detected in the SIGNAL symbol. For HiperLan/2 signals, the value is specified as 1e10, meaning that the value does not apply and should be displayed as "N/A".

•	vsaTrcDemOFDMErrInfoCodingRateDen - The denominator of the coding rate of the convolutional coder, as detected in the SIGNAL symbol. For HiperLan/2 signals, the value is specified as 1e10, meaning that the value does not apply and should be displayed as "N/A".

•	vsaTrcDemOFDMErrInfoBitsPerSym - The number of bits per symbol per subcarrier, determined by the modulation format specified in the SIGNAL symbol. For HiperLan/2 signals, the value is specified as 1e10, meaning that the value does not apply and should be displayed as "N/A".

•	vsaTrcDemOFDMErrInfoBitRate - The calculated decoded bit rate of the signal, computed from the detected coding rate and modulation type in the SIGNAL symbol, and from the symbol rate as specified by the user. For HiperLan/2 signals, the value is specified as 1e10, meaning that the value does not apply and should be displayed as "N/A".


DemodOFDMSubcarStrt

(Option B7R only)

This is a Data Header variable.

Type = Long

DemodOFDMSubcarStrt value is the first subcarrier index represented in the data. For 802.11a and HiperLan/2 data, the first used subcarrier index is always −26, because the subcarriers are numbered −26 to +26.

This variable is present on all OFDM measurement data that has different values for each subcarrier. This is most OFDM measurment data, including IQ Meas, IQ Ref, Error Vector Spec, Syms/Errs, and Eq Freq.

This variable is used by the display and marker code to compute the correct subcarrier number to annotate the display.


DemodOFDMSubcarType

(Option B7R only)

This is a Data Header variable.

Type = Array of Short

Each DemodOFDMSubcarType value in the array specifies the type of subcarrier in the corresponding measurement data. If the subcarrier is an unused subcarrier (like the middle subcarrier in 802.11a), the subcarrier type value will be zero. If the subcarrier is a data subcarrier, the value will be one. If the subcarrier is a pilot subcarrier, the value will be two.

This variable is used by the display code to decide how to color each data point. Points for unused subcarriers are not plotted at all; points for data subcarriers are plotted with the normal data color; and points for pilot subcarriers are plotted with the pilot color.

Usually the length of the array is equal to the number of different subcarriers in the data, so for 802.11a and HiperLan/2 the array length is usually 53. However, for Error Vector Time data the length of the array is equal to the length of the data.

If the actual measurement data is longer than the subcarrier type array (which it normally is for all data except Error Vector Time), it is assumed that the subcarrier type array is reused over and over to specify the type each subcarrier in the data.


DemodOutPtsPerSym

(Option AYA only)

This is a Data Header variable.

Type = Long

DemodOutputPtsPerSymbol indicates the number of Digital Demod points / symbol in the demodulated trace results.


DemodStatePos

(Option AYA only)

This is a Data Header variable.

Type = Array of Float

DemodStatePos is an array of ideal state position pairs (real, imag) for this digital demodulation format.


DemodSymbolRate

(Option AYA only)

This is a Data Header variable.

Type = Float

DemodSymbolRate indicates the Digital Demod symbol rate.


DemodType

(Option AYA only)

This is a Data Header variable.

Type = Short

DemodType indicates the format of digital demod measurement.

For a list of values and the corresponding demod type, see VsaDigDemodFormat in the COM API Constants Table.


FreqValidMax

This is a Data Header variable.

Type = Double

FreqValidMax indicates the maximum displayable frequency from the recalled trace. This variable is related to display blanking, which is described under Stop Frequency.


FreqValidMin

This is a Data Header variable.

Type = Double

FreqValidMin indicates the minimum displayable frequency from the recalled trace. This variable is related to display blanking, which is described under Start Frequency.


InputBlockSize

This is a Data Header variable.

Type = Long

InputBlockSize indicates how big a blocksize will be used for the FFT of this input time data. The time data will be zero-padded to make it that big. The value is calculated from the user's requested number of frequency points (401 lines → blocksize of 512 for zoom or 1024 for baseband). This variable should only be present on time data.

See Also

Frequency points


InputCenter

This is a Data Header variable.

Type = Double

InputCenter indicates the center frequency of the input data in Hz.


Input Connector

This is a Data Header variable.

Type = Short

InputConnector indicates the input hardware connector type setting for the data.

0 = Unbalanced

1 = Balanced


InputImpedance

This is a Data Header variable.

Type = Double

InputImpedance indicates the input impedance setting for the data in Ohms.


InputRange

This is a Data Header variable.

Type = Double

InputRange indicates the input hardware range setting for the data in Volts peak.


InputRange1

This is a Data Header variable.

Type = Double

InputRange1 indicates the input hardware range setting for the data in Volts peak. This variable appears only if the trace data is from channel 1 in a 2-channel analyzer.


InputRange2

This is a Data Header variable.

Type = Double

InputRange2 indicates the input hardware range setting for the data in Volts peak. This variable appears only if the trace data is from channel 2 in a 2-channel analyzer.


InputRefImped

This is a Data Header variable.

Type = Double

InputRefImped indicates the input reference impedance setting for the data in Ohms.


InputSpan

This is a Data Header variable.

For files you save from another application and want to recall into an 89600 analyzer, you can specify an input span and a sample rate (by specifying Xdelta). If the ratio of the two is not 1.28 (zoomed) or 2.56 (baseband), the analyzer resamples the data.


InputZoom

This is a Data Header variable.

Type = Boolean

If InputZoom is true, the input was zoomed rather than baseband. This implies that time data is complex.


MinMax

(Spectrum Analyzer measurements only)

This is a Data Header variable.

Type = Boolean

If MinMax is True, this data represents 2 points per X value (Min/Max pairs). The Y data lists the minimum value in the left column and maximum value in the right column.


PassThru

(Spectrum Analyzer measurements only)

This is a Data Header variable.

Type = Boolean

If PassThru is true, the data has too many points to average and is passed through the average step.


PdfRangeError

This is a Data Header variable.

Type = Boolean

If PdfRangeError is true, the internal CCDF histogram overflowed. This can happen only if the signal RMS level changes drastically during the measurement.

This variable applies only for CCDF traces.


PdfRmsLevel

This is a Data Header variable.

Type = Double

PdrRmsLevel indicates the overall signal RMS level in Vrms.

This variable applies only for PDF, CDF, and CCDF traces.


PdfUnit

This is a Data Header variable.

Type = String

This variable is a string which identifies the units of the X axis of a CCDF, PDF, or CDF trace. Typically this would be "V" (for "Volts"), but it can take on other values during an analog demodulation measurement.


PowerData

This is a Data Header variable.

Type = Boolean

If PowerData is true, the data is power data. This implies that the data is real rather than complex, and that the values have been squared.


ResBW

This is a Data Header variable.

Type = Double

ResBW indicates the resolution bandwidth of the data.


S_TimeSec

This is a Data Header variable.

Type = Double array

This is the time offset (in seconds) of when the each scan of data was acquired relative to the start of the spectrogram. This array has a value for each scan allocated in the spectrogram.


SweepDone

(Spectrum Analyzer measurements only)

This is a Data Header variable.

Type = Boolean

A true value for SweepDone indicates this result contains data from an entire sweep.

For more information, see Setting Up a Swept Measurement.


SweepOverload

This is a Data Header variable.

Type = Long

SweepOverload indicates the number of overloads in the displayed sweep. 0 = no overloads, any number greater than 0 indicates overloads occurred.


SwpTime

This is a Data Header variable.

Type = Double

For vector measurements:

•	If the data is time data, SwpTime indicates the total time length of the data.

•	If the data is frequency data, SwpTime indicates the total time length of the time data that was used to calculate the frequency data.

See Also

Sweep time


T_Aperture

This is a Data Header variable.

Type: Short

T_Aperture indicates the value of the Delay Aperture when the trace was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_DemodCodeOrder

This is a Data Header variable.

Type = Short

T_DemodCodeOrder is the displayed code order for the 3G CDP data: 0 = Hadamard, 1 = Bit Reverse. This is available for both cdma2000 and W-CDMA measurements.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_DemodFreqUnit

This is a Data Header variable.

Type = Short

The value of T_DemodFreqUnit indicates whether the x- or z-axis units (if appicable) were hertz (0) or carrier (1) when the trace was saved. This only applies if either the x- or z-axis units are frequency units.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_DemodStateShape

This is a Data Header variable.

Type = Short

The value of T_DemodStateShape indicates the shape of the Ideal State.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_DemodStateSize

This is a Data Header variable.

Type = Short

The value of T_DemodState Size indicates the ideal state size as a percentage.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_DemodSymbolShape

This is a Data Header variable.

Type = Short

The value of T_DemodSymbolShape indicates the Symbol Shape when the trace was saved.

0 = None

1 = Dots

2 = Bars

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_DemodTblFormat

This is a Data Header variable.

Type = Short

The value of T_DemodTblFormat indicates whether the Demod Symbol Table is in binary (0) or hexadecimal (1) format.

The T_ variables describe the setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the settings to their settings when the trace was saved.


T_DemodTimeUnit

This is a Data Header variable.

Type = Short

The value of T_DemodTimeUnit indicates whether the x- or z-axis units (if appicable) were seconds (0) or symbols (1) when the trace was saved. This only applies if either the x- or z-axis units are time units.The T_ variables describe the display setup when the trace was saved.

When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_PhsOffset

This is a Data Header variable.

Type = Short

The value of T_PhsOffset indicates the setting for Phase Offset.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_TrigRefLineVis

This is a Data Header variable.

Type = Boolean

T_TrigRefLineVis indicates whether the trigger reference line was visible when the trace was saved.


T_UnwrapRef

This is a Data Header variable.

Type = Short

The value of T_UnwrapRef indicates the Unwrap Reference when the trace was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_VectXCtr

This is a Data Header variable.

Type = Short

T_VectXCtr indicates the value of Vector X Center when the trace was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_XEyeLength

This is a Data Header variable.

Type = Short

T_XEyeLength is the Trace Demod eye length

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_XLeft

This is a Data Header variable.

Type = Double

T_XLeft indicates the Left reference value when the trace was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_XLog

This is a Data Header variable.

Type = Boolean

If Trace_X log is true, the X-axis scale was logarithmic when the trace was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_XRight

This is a Data Header variable.

Type = Double

T_XRight indicates the Right reference value when the trace was saved.


T_XScaleAuto

This is a Data Header variable.

Type = Boolean

If T_XscaleAuto is true, the X axis was set to Full Scale when the data was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_YBottom

This is a Data Header variable.

Type = Double

T_YBottom indicates the Y Bottom value when the measurement was taken.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_YCoordinate

This is a Data Header variable.

Type = Short

T_YCoordinate indicates the Y-axis coordinates when the measurement was taken. The value is an integer. For a list of the coordinates corresponding to each value, see the list for VsaTrcFormat in the COM API Constants Table.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_YRefPos

This is a Data Header variable.

Type = Float

T_YRefPos indicates the reference position for the Y axis (0.0 = bottom of screen, 1.0 = top of screen) when the measurement was taken.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_YRefVisible

This is a Data Header variable.

Type = Boolean

T_RefVisible indicates whether the Trace Y Reference Line was visible when the trace was saved.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_YTop

This is a Data Header variable.

Type = Double

T_YTop indicates the value for Y Top when the measurement was taken.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


T_Yunit

This is a Data Header variable.

Type = Short

T_YUnit is a value which indicates whether the Y-axis units were power or not when the trace was saved. For a list of the unit associated with each value, see VsaTrcYUnit in the COM API Constants Table.

The T_ variables describe the display setup when the trace was saved. When you recall and display a saved trace, the analyzer uses the T_ variables to restore the display settings to their settings when the trace was saved.


TimeSec

This is a Data Header variable.

Type = Double

TimeSec is the time offset (in seconds) of when the current scan of data was acquired relative to the start of the spectrogram.


TimeString

This is a Data Header variable.

Type = String

TimeString indicates the local time when the data was measured.


TotalPdfPoints

This is a Data Header variable.

Type = Double

TotalPdfPoints indicates the total number of input samples that were used to produce the histogram.

This variable applies only for PDF, CDF, and CCDF traces.


TrcLedBits

This is a Data Header variable.

Type = Long

TrcLedBits is a priority-ordered set of bits indicating all trace indicator conditions that are present. Only the highest priority indicator is resolved into TrcLedStr. The order of priority is:

Bit	Indicator condition
0x1	NO DATA
0x2	DATA?
0x4	OVx
0x10	CAL?
0x40	PULSE NOT FOUND
0x80	SYNC NOT FOUND
0x400	CARRIER LOCK?
0x800	EQ
0x1000	RNG
0x2000	ALL PTS
0x4000	MEAS OFFSET?
0x8000	INACTIVE CHAN
0x10000	PULSE TOO SHORT


TrcLedBold

This is a Data Header variable.

Reserved for future use.


TrcLedReason

This is a Data Header variable.

Type = String

When TrcLedReason is available, it gives a detailed reason for the Trace Led (TrcLedStr). When TrcLedReason is not available, this defaults to the TrcLedStr.

When you click on a Trace indicator, the TrcLedReason is displayed.


TrcLedStr

This is a Data Header variable.

Type = String

When TrcLedStr is available, it contains the trace LED string. The LED string is displayed in the Trace indicator. For a list of possible strings, see Trace indicators .


TrcTtl

This is a Data Header variable.

Type = String

The TrcTtl indicates the type of data that is displayed in the trace, for example "Ch1 Spectrum" or "Ch1 Main Time." This is the same information that is displayed above the upper left portion of the grid area, the Trace Title.


TriggerType

This is a Data Header variable.

Type = Short

TriggerType indicates what type of triggering was used when the measurement was taken.

For a list of the average type associated with each value, see the list for VsaAvgStyle in the COM API Constants Table.


TS_ColorCount

This is a Data Header variable.

Type = Short

TS_ColorCount is the number of displayed colors in the spectrogram when this trace was saved.


TS_ColorMap

This is a Data Header variable.

Type = Short

TS_ColorMap is the spectrogram map color scheme selected when the trace was saved.


TS_Enhance

This is a Data Header variable.

Type = Double

TS_Enhance is the spectrogram enhance factor selected when the trace was saved.


TS_Threshold

This is a Data Header variable.

Type = Double

TS_Threshold is the spectrogram threshold value selected when the trace was saved.


TS_Visible

This is a Data Header variable.

Type = Boolean

TS_Visible indicates whether the spectrogram was visible when the trace was saved.


WindowType

This is a Data Header variable.

Type = String

For time data, WindowType indicates what window will be used when doing an FFT of this data.

For frequency data, WindowType indicates the window that was used for the FFT.

Possible values:

UNIFORM

HANN

GAUSSTOP

FLATTOP


XDelta

This is a Data Header variable.

Type = Double

For time data, XDelta indicates the time difference between two adjacent points. The sample rate is (1 / XDelta).

For frequency data, XDelta indicates the frequency difference between two adjacent points.


XDomain

This is a Data Header variable.

Type = Short

XDomain indicates what domain the data is. The domain depends on the type of data displayed in the trace.

0 = Unknown

1 = Frequency

2 = Time

3 = Channel

4 = Amplitude


XPtsPerSymbol

This is a Data Header variable.

Type = Long

When this data is a digital demodulated time record, XPtsPerSymbol is the points / symbol dot of demodulated data. For QQSPK this is 1/2 DemodOutputPtsPerSymbol.


XSegmentDelta

(Option B7R only)

This is a Data Header variable.

Type = Double

For OFDM Error Vector Spectrum data, XSegmentDelta indicates the z-axis time difference between each spectrum vector. For OFDM Error Vector Time data, XSegmentDelta indicates the z-axis frequency difference between each time vector.


XSegmentDomain

(Option B7R only)

This is a Data Header variable.

Type = Short

XSegmentDomain indicates the domain of the z axis. The domain depends upon the type of data displayed in the trace. OFDM Error Vector Spectrum has an XSegmentDomain = 2 (Time) and Error Vector Time has an XSegmentDomain = 1 (Frequency).

0 = Unknown

1 = Frequency

2 = Time

3 = Channel

4 = Amplitude


XSegmentLen

(Option B7R only)

This is a Data Header variable.

Type = Long

When OFDM data has a z-axis (e.g. Error Vector Spectrum), XSegmentLen is the number of consecutive number of x-y pairs associated with each z-axis value. For example, with Error Vector Spectrum, XSegmentLen is the number of carriers in each symbol.


XSegmentStart

(Option B7R only)

This is a Data Header variable.

Type = Double

XSegmentStart indicates the z-axis value of the first XSegmentLen points of the data.


XSegmentUnit

(Option B7R only)

This is a Data Header variable.

Type = String

XSegmentUnit is a string indicating the z-axis units, for example Hz or Sec. The units depend on the domain (XSegmentDomain) of the z axis.


XStart

This is a Data Header variable.

Type = Double

XStart indicates the X value of first point in data (start frequency).


XUnit

This is a Data Header variable.

Type = String

XUnit is a string indicating the X axis units, for example "Hz" or "Sec". The units depend on the domain of the displayed data.


XValidMax

This is a Data Header variable.

Type = Long

XValidMax is the last point in the spectrum that is normally displayed if part of the data is outside of the instrument's specifications.


XValidMin

This is a Data Header variable.

Type = Long

XValidMin is the first point in the spectrum that is normally displayed if part of the data is outside of the instrument's specifications.


Y

This is a Data Header variable.

Type = Array of numbers

Y is the actual measurement data. If this is complex data, the data is in real/imaginary pairs. For the Spectrum Analyzer application, the data is in min/max pairs.


 Y1

This is a Data Header variable.

Type = Array of numbers

Y1 is the actual measurement data. If this is complex data, the data is in real/imaginary pairs. For the Spectrum Analyzer application, the data is in min/max pairs.This variable appears only if the trace data is from channel 1 of a 2-channel measurement.


 Y2

This is a Data Header variable.

Type = Array of numbers

Y2 is the actual measurement data. If this is complex data, the data is in real/imaginary pairs. For the Spectrum Analyzer application, the data is in min/max pairs.This variable appears only if the trace data is from channel 2 of a 2-channel measurement.


YUnit

This is a Data Header variable.

Type = String

YUnit is a string indicating the Y axis units, for example, "V" or "dBm". The Y axis units depend on the kind of data displayed.

See Also

T_YUnit


ZeroPadding

This is a Data Header variable.

Type = Double

ZeroPadding is a ratio (0.0 to 1.0) indicating how much zero padding to add to the time data before converting to frequency domain: 0 = no padding, 1.0 is all padding

For time data only, this is the zero-padding ratio for a subsequent FFT. For frequency data this number is used to determine the time length for an FFT.

See Also

Time records and frequency data


How To Use This Help File

To do this...	Click...
Display or hide the navigation pane (Contents, Index, and Search tabs)...
Display the documentation roadmap...
Browse through the online topics...
View the Table of Contents…
Display the online help index...
Search for a word or phrase...
Display a history of topics that you’ve visited…
To print a single topic...
To print an entire Book…	(in the Table of Contents)
To change the displayed font size…


Acknowledgements

The following products are mentioned in one or more places in the Agilent 89600-series documentation.

Product	Acknowledgement
Adobe® and Acrobat®	These products are trademarks of Adobe Systems Incorporated.
Microsoft®, Windows NT®, Windows®, and MS Windows®	These products are U.S. registered trademarks of Microsoft Corporation.
MS Excel, MS Word, MS Office, VBScript	These products are products of Microsoft Corporation.
MATLAB	MATLAB is a product of The MathWorks, Inc.


The Documentation Roadmap is not installed on your system.


1999-2002, Agilent Technologies


This documentation is not installed on your system.


This document was not available for inclusion in the online help. You can download the PDF from the 89600 [image] Web page .


This document was not available for inclusion in the online help. You can download the PDF from the 89600 [image] Web page .


This document was not available for inclusion in the online help. You can download the PDF from the 89600 [image] Web page .